Skip to main content

Reply to this post | Go Back
View Post [edit]

Poster: Nemo_bis Date: Aug 2, 2014 8:06am
Forum: texts Subject: Dealing with '-fast' OCR

What's the best course of action when seeing "Doing '-fast' OCR, due to high load on OCR nodes"?

For instance the following jobs, lasted 2.5, 1.9 and 2.3 h: (JP2 images of 290, 180, 190 MB) vs. 8.8 h of a similar non-fast one (430 MB JP2).

Fast OCR is still wonderful, and hopefully a fast OCR of better images is still better than a non-fast OCR of low resolution images (as ). But if/when someone wanted to manually proofread the OCR, it would be silly to waste manual time for needless corrections.

How better is the non-fast OCR? Should one hope for a non-fast OCR, e.g. submitting only when servers are not overloaded? (Is there even a way to do that, or to lower priority of one's own jobs?) Or should one just ask IA staff to rerun derive when a precise OCR is especially needed?